Skip to content

arm64: dts: apple: t6050-k114c: boot NOR and read-only nvram partition - #1738

Draft
joshuaswarren wants to merge 1 commit into
aurora-silicon:integration/aurorafrom
joshuaswarren:w88/k114c-nor-nvram
Draft

joshuaswarren wants to merge 1 commit into
aurora-silicon:integration/aurorafrom
joshuaswarren:w88/k114c-nor-nvram

Conversation

@joshuaswarren

@joshuaswarren joshuaswarren commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Status note: the head moved to 6b26ff4 on 2026-11-18 (rebased onto integration/aurora 0abc2f3); CI is rerunning at that head. Everything below describes the earlier state unless it carries its own head.

[Joshua's agent] Draft until a boot proof lands.

Enables the QSPI controller on the 14-inch M5 Max with a jedec,spi-nor flash on chip select 0 and a read-only nvram partition, plus the nvram alias, so the boot-state tool can read the boot variables. spi-apple-qspi needs no board entry for reads: the T8140 compatible already allows data reads, and the board table only gates writes. Writes are not part of this change.

Checked: the K114c dtb builds on the integration tree, and this change adds no dtc warning (the base prints seven for it, with and without this change). Not yet booted. Boot proof: the spi-nor identify line, an "nvram" entry in /proc/mtd, and the boot-state tool reading back the boot target and volumes.

Validated on, and reach

Validated on: The K114c dtb builds, with the same seven dtc warnings as the base. Not booted.

Applies beyond the M4: No. A K114c device-tree change. The T8140 compatible already allows data reads; writes are not part of it.

m tester run (omarchy-m-testing.org): feature rows Boot chain. The tester needs the hardware; no tester run is linked to this change.

Rebased onto integration/aurora 514ae1f (head a836dce)

The branch conflicted with the base in t6050-k114c.dts: the base appended the left-front USB-C port block at the end of the file, where this change appends the NOR block. I kept both (the base's block first) and added the nvram alias after bluetooth0. The commit message and author are unchanged. The K114c dtb builds on the 13-inch M1 MacBook at this head (gcc 16.1.1, W=1). The seven dtc warnings are six reserved-memory unit-name ones from t6050-k114c-gpu.dtsi and one for pmp@284e00000; the base prints the same seven. This head was not booted.

@joshuaswarren

Copy link
Copy Markdown
Contributor Author

GREEN on a836dce
Model: zai/glm-5.3

Rebase verified three-way. Base-to-head is exactly two additions: the nvram alias after bluetooth0 in the base's aliases node, and the 26-line boot NOR block appended after the base's left-front USB-C block - both kept, base first, nothing else touched. The old-head comparison shows the only other deltas are the base additions the old head predates, so this PR's own content is unchanged from fc3a41a. The corrected body now says what a run on this base actually shows: the dtb builds with the same seven dtc warnings the base prints, with and without this change, and the earlier no-warning wording is gone from both the Checked line and the Validated-on section. Read-only scope, spi-nor identify and /proc/mtd named as the boot proof, not-booted stated. The alias placement is where the base's alias list lives, so the resolution matches the description exactly.

Model: zai/glm-5.3 (live from lane_models.py this turn).

…partition

Enable the QSPI controller with a jedec,spi-nor flash on chip select 0 and
the 0xc0000-byte nvram partition at 0x700000, read-only, so asahi-bless can
read the boot state. The flash ID is probed by spi-nor.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant